Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix for issue 159: Changing a disk image is now propagated to the VMs #161

Conversation

yannickstruyf3
Copy link
Collaborator

@yannickstruyf3 yannickstruyf3 commented Aug 7, 2020

Suggested fix for #159
Changing the image for a VM is propagated via the API to the VM.

fix #159

@ghost ghost added the size/L label Aug 7, 2020
@yannickstruyf3 yannickstruyf3 force-pushed the bugfix/fix-159-imagereplace branch from bed4371 to bc45f4b Compare August 7, 2020 11:14
@ghost ghost added size/XL and removed size/L labels Aug 7, 2020
@yannickstruyf3 yannickstruyf3 force-pushed the bugfix/fix-159-imagereplace branch from bc45f4b to 31550e2 Compare August 7, 2020 11:21
@ghost ghost added size/XXL dependencies and removed size/XL labels Aug 7, 2020
@yannickstruyf3 yannickstruyf3 force-pushed the bugfix/fix-159-imagereplace branch from 31550e2 to 10f7c01 Compare August 7, 2020 11:31
@yannickstruyf3
Copy link
Collaborator Author

Did not meet QA reqs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Modifying VM image uuid (data_source_reference in disk_list) does not replace Disk
1 participant